The publish function only seems to work for publishing package on pypi.org or test.pypi.org and as I'm working primarily with a private company repository this was not ideal. Even though I used Rye for managing the whole project, I had to use Twine in a separate flow to publish the package.

After some initial discussions it turned out that Rye is using twine internally to publish packages, and there were thus no real reason why it was not working. After digging into it, the publish command basically wraps Twine, but it also adds a lot of fairly complicated checks and the parameters given to Twine was hard-coded to be a specific set of arguments adapted to publishing on pypi.org.

Commenting out the absolute majority of the additional command parsing made it work almost directly.

I just need to figure out what the rest of the commented code does and if we can remove it or if we have to adapt it.